- install
itools
brew tap githubutilities/tap
brew cask install itools246| #!/usr/bin/env zx | |
| // | |
| // resolveIdentity() falls back from exact-label match to "the sole identity | |
| // with this touch policy" so a key created by hand before this script existed | |
| // gets adopted rather than duplicated; ambiguous cases die rather than guess. | |
| // --cleanup deletes by resolved identity one at a time, never via | |
| // `sc_auth delete-all-ctk-identities`, so unrelated FileVault/PIV/login | |
| // smartcard identities are never touched. | |
| import os from 'node:os'; |
Tracks down when a Minecraft account was created.
Mojang has an API endpoint for usernames:
https://api.mojang.com/users/profiles/minecraft/<name>?at=<timestamp>
It can be used to find the UUID of an account, by username it used at the given time.
It returns either 200 OK or 204 No Content β indicating that the username was not in use at the time.
A pattern for building personal knowledge bases using LLMs.
This is an idea file, it is designed to be copy pasted to your own LLM Agent (e.g. OpenAI Codex, Claude Code, OpenCode / Pi, or etc.). Its goal is to communicate the high level idea, but your agent will build out the specifics in collaboration with you.
Most people's experience with LLMs and documents looks like RAG: you upload a collection of files, the LLM retrieves relevant chunks at query time, and generates an answer. This works, but the LLM is rediscovering knowledge from scratch on every question. There's no accumulation. Ask a subtle question that requires synthesizing five documents, and the LLM has to find and piece together the relevant fragments every time. Nothing is built up. NotebookLM, ChatGPT file uploads, and most RAG systems work this way.
LLM observability is the practice of monitoring and tracing AI applications to understand LLM calls, prompts, token usage, latency, costs, tool calls, retrieval, agent trajectories, errors, and output quality in production.
For production AI systems, logging only the final LLM response is not enough.
You need visibility across:
See how a minor change to your commit message style can make a difference.
git commit -m"<type>(<optional scope>): <description>" \ -m"<optional body>" \ -m"<optional footer>"
| # Obtained with the code written in next file | |
| emoji_grinning_face=π | |
| emoji_grinning_face_with_big_eyes=π | |
| emoji_grinning_face_with_smiling_eyes=π | |
| emoji_beaming_face_with_smiling_eyes=π | |
| emoji_grinning_squinting_face=π | |
| emoji_grinning_face_with_sweat=π | |
| emoji_rolling_on_the_floor_laughing=π€£ | |
| emoji_face_with_tears_of_joy=π | |
| emoji_slightly_smiling_face=π |
how to leverage oracle's temping offers
The limits of the free tier say that you can create up to 4 instances.
[!WARNING]